home *** CD-ROM | disk | FTP | other *** search
-
-
-
- PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111)))) PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- ppppmmmmnnnnssssccccoooommmmpppp - compile an ASCII performance metrics namespace into binary
- format.
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- ppppmmmmnnnnssssccccoooommmmpppp [----dddd] [----ffff] [----nnnn _n_a_m_e_s_p_a_c_e] [----vvvv _v_e_r_s_i_o_n] _o_u_t_f_i_l_e
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- ppppmmmmnnnnssssccccoooommmmpppp compiles a Performance Metrics Name Space (PMNS) in ASCII format
- into a more efficient binary representation. ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3) is able
- to load this binary representation significantly faster than the
- equivalent ASCII representation.
-
- If _o_u_t_f_i_l_e already exists ppppmmmmnnnnssssccccoooommmmpppp will exit without overwriting it.
-
- By convention, the name of the compiled namespace is that of the root
- file of the ASCII namespace, with ....bbbbiiiinnnn appended. For example, the root
- of the default PMNS is a file named rrrrooooooootttt and the compiled version of the
- entire namespace is rrrrooooooootttt....bbbbiiiinnnn.
-
- The options are;
-
- ----dddd By default the PMNS to be compiled is expected to contain at most
- one name for each unique Performance Metric Id (PMID). The ----dddd
- option relaxes this restriction and allows the compilation of a PMNS
- in which multiple names may be associated with a single PMID.
- Duplicate names are useful when a particular metric may be logically
- associated with more than one group of related metrics, or when it
- is desired to create abbreviated aliases to name a set of frequently
- used metrics.
-
- ----ffff Force overwriting of an existing _o_u_t_f_i_l_e if it already exists.
-
- ----nnnn Normally ppppmmmmnnnnssssccccoooommmmpppp operates on the default PMNS, however if the ----nnnn
- option is specified an alternative namespace is loaded from the file
- _n_a_m_e_s_p_a_c_e.
-
- ----vvvv By default, ppppmmmmnnnnssssccccoooommmmpppp writes a version 0000 compiled namespace, which is
- compatible with versions of PCP before PCP2.0. If _v_e_r_s_i_o_n is 1111 then
- ppppmmmmnnnnssssccccoooommmmpppp will write a version 1111 namespace which is compatible with
- PCP2.0 or later. Note that PCP version 2.0 or later can handle both
- versions but PCP versions prior to PCP 2.0 can only handle version 0000
- compiled namespaces.
-
- The default input PMNS is found in the file $_P_C_P__V_A_R__D_I_R/_p_m_n_s/_r_o_o_t unless
- the environment variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is set, in which case the value is
- assumed to be the pathname to the file containing the default input PMNS.
-
- CCCCAAAAVVVVEEEEAAAATTTT
- Once the writing of the new _o_u_t_f_i_l_e has begun, the signals SIGINT, SIGHUP
- and SIGTERM will be ignored to protect the integrity of the new file.
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111)))) PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111))))
-
-
-
- FFFFIIIILLLLEEEESSSS
- $_P_C_P__V_A_R__D_I_R/_p_m_n_s/*
- default PMNS specification files
- $_P_C_P__V_A_R__D_I_R/_p_m_n_s/_r_o_o_t._b_i_n
- compiled version of the default PMNS, when the environment
- variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT is unset
- $_P_C_P__V_A_R__D_I_R/_p_m_n_s/_s_t_d_p_m_i_d
- some standard macros for PMID generation
-
- PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
- Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the
- file and directory names used by PCP. On each installation, the file
- /_e_t_c/_p_c_p._c_o_n_f contains the local values for these variables. The
- $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration
- file, as described in ppppccccpppp....ccccoooonnnnffff(4).
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ppppmmmmnnnnssssaaaadddddddd(1), ppppmmmmnnnnssssddddeeeellll(1), ppppmmmmnnnnssssmmmmeeeerrrrggggeeee(1), PPPPMMMMAAAAPPPPIIII(3), ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3),
- ppppccccpppp....ccccoooonnnnffff(4), ppppccccpppp....eeeennnnvvvv(4) and ppppmmmmnnnnssss(4).
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- Cannot open ``xyz'' - the filename for the root of the PMNS that was
- passed to ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3) is bogus.
-
- Illegal PMID - either one of the three PMID components (see ppppmmmmnnnnssss(4)) is
- not an integer, or the value for one of the components is negative, or
- too large.
-
- Expected ... - specific syntax errors when a particular type of lexical
- symbol was expected and not found; the messages are intended to be self-
- explanatory.
-
- Internal botch - implementation problem for the parser ...
-
- Duplicate name ``abc'' in subtree for ``pqr.xyz'' - for each non-leaf
- node, the names of all immediate descendents must be unique.
-
- No name space entry for ``root'' - the special non-leaf node with a
- pathname of ``root'' defines the root of the PMNS, and must appear
- somewhere in the PMNS specification.
-
- Multiple name space entries for ``root'' - more than one ``root'' node
- does not make sense!
-
- Disconnected subtree (``abc.xyz.def'') in name space - the pathname for
- this non-leaf node does not correspond to any pathname in the PMNS, hence
- this non-leaf node is ``orphaned'' in the PMNS.
-
- Cannot find definition for non-terminal node ``xyz'' in name space - a
- non-terminal node is named as part of its parent's specification, but is
- never defined.
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-
-
-
- PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111)))) PPPPMMMMNNNNSSSSCCCCOOOOMMMMPPPP((((1111))))
-
-
-
- Duplicate metric id (xxx) in name space for metrics ``abc'' and ``xyz'' -
- each PMID must be unique across the PMNS.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 3333
-
-
-
-